Data processing apparatus that enables import/export of setting value, control method therefor, and storage medium storing control program therefor

ABSTRACT

A data processing apparatus that is capable of reducing the garbling of characters caused by the difference among the character codes when setting data are transferred to another apparatus by the import-export function. A storage unit stores setting data for the data processing apparatus. A receiving unit receives an instruction for exporting the setting data stored in the storage unit. A converting unit converts Unicode data included in the setting data into character code data of language, which is set to the data processing apparatus. An export unit exports the character code data converted by the converting unit and the Unicode data.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a data processing apparatus thatenables import/export of a setting value, a control method therefor, anda storage medium storing control program therefor.

2. Description of the Related Art

Image forming apparatuses, such as copying machines and facsimilemachines, in recent years have many user set items with highperformance, and tend to increase time and effort of a user whoregisters setting values (setting data) for the user set items.Accordingly, there is an apparatus that is provided with animport-export function that enables to bring setting data of a certainapparatus out and to register the setting data to another apparatus ofthe same kind or a different kind as a technique that simplifiesregistration of a series of setting values.

However, an import-export function of a conventional image formingapparatus did not consider a case where character codes are differentamong image forming apparatuses. Accordingly, import of character stringdata of a character code that is not supported by an import imageforming apparatus causes a problem that the characters are not displayedcorrectly due to garbling.

On the other hand, there is a technique that converts a character codein order to absorb the difference among the character codes supported bydifferent apparatuses. For example, Japanese Laid-Open PatentPublication (Kokai) No. 2000-207392 (JP 2000-207392A) proposes atechnique that converts document data in a character code of a host intodata in a character code of a printer, reads fonts corresponding to theconverted data from a memory, and outputs the fonts to the printer.

SUMMARY OF THE INVENTION

The present invention provides a data processing apparatus, a controlmethod therefor, and a storage medium storing a control programtherefor, which are capable of reducing the garbling of characterscaused by the difference among the character codes when setting data aretransferred to another apparatus by the import-export function.

Accordingly, a first aspect of the present invention provides a dataprocessing apparatus comprising a storage unit configured to storesetting data for the data processing apparatus, a receiving unitconfigured to receive an instruction for exporting the setting datastored in the storage unit, a converting unit configured to convertUnicode data included in the setting data into character code data oflanguage, which is set to the data processing apparatus, and an exportunit configured to export the character code data converted by theconverting unit and the Unicode data.

Accordingly, a second aspect of the present invention provides a dataprocessing apparatus comprising a store storage unit configured to storesetting data for the data processing apparatus, a receiving unitconfigured to receive an instruction for importing setting data of thedata processing apparatus, a converting unit configured to convertcharacter code data included in the setting data that is not Unicodedata into Unicode data, and an import unit configured to import theUnicode data converted by the converting unit when the setting dataimported according to an instruction received by the receiving unit isnot Unicode data, and to import data without conversion by theconverting unit when the setting data imported according to theinstruction is Unicode data.

Accordingly, a third aspect of the present invention provides a controlmethod for a data processing apparatus comprising storing setting datafor the data processing apparatus, receiving an instruction forexporting the stored setting data, converting Unicode data included inthe setting data into character code data of language, which is set tothe data processing apparatus, and exporting the character code dataconverted in the converting and the Unicode data.

Accordingly, a fourth aspect of the present invention provides a controlmethod for a data processing apparatus comprising storing setting datafor the data processing apparatus, receiving an instruction forimporting setting data for the data processing apparatus, convertingcharacter code data included in the setting data that is not Unicodedata into Unicode data, and importing the Unicode data converted by theconverting when the setting data imported according to an instructionreceived in the receiving is not Unicode data, and importing datawithout converting when the setting data imported according to theinstruction is Unicode data.

Accordingly, a fifth aspect of the present invention provides anon-transitory computer-readable storage medium storing acomputer-readable program and the program computer executable codes toperform the control method according to the third aspect.

Accordingly, a sixth aspect of the present invention provides anon-transitory computer-readable storage medium storing acomputer-readable program and the program computer executable codes toperform the control method according to the fourth aspect.

The present invention is capable of reducing the garbling of characterscaused by the difference among the character codes when setting data istransferred to another apparatus by the import-export function.

Further features of the present invention will become apparent from thefollowing description of exemplary embodiments with reference to theattached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a view showing a setting value management system that includesan image forming apparatus according to the embodiment.

FIG. 2 is a block diagram schematically showing a configuration of theimage forming apparatus shown in FIG. 1.

FIG. 3 is a block diagram schematically showing a functionalconfiguration of an image forming apparatus in a group of managed objectapparatuses shown in FIG. 1.

FIG. 4 is a view showing an example of setting data read from a devicesetting file database (DB) by a device setting management module shownin FIG. 3.

FIG. 5 is a view showing an example of a device setting file generatedby the device setting management module shown in FIG. 3.

FIG. 6 is a view showing a language setting of the image formingapparatus shown in FIG. 2.

FIG. 7 is a flowchart showing a device setting file generation processexecuted by a CPU shown in FIG. 2.

FIG. 8 is a view showing contents of the device setting file DBinitialized by the device setting management module.

FIG. 9 is a flowchart showing procedures of a registration processexecuted by the CPU shown in FIG. 2 to register a device setting file tothe device setting file DB.

FIG. 10 is a view showing an example of a device setting file.

FIG. 11 is a view showing contents of the device-setting-file DB afterthe registration process shown in FIG. 10.

FIG. 12A is a view showing a screen before import displayed on an LCDpanel shown in FIG. 2.

FIG. 12B is a view showing a screen after the import displayed on theLCD panel shown in FIG. 2.

FIG. 13A is a view showing contents of the device-setting-file DB beforeregistering the contents of the device setting file shown in FIG. 10into an image forming apparatus that employs a different character code.

FIG. 13B is a view showing contents of the device-setting-file DB afterregistering the contents of the device setting file shown in FIG. 10into the image forming apparatus that employs the different charactercode.

DESCRIPTION OF THE EMBODIMENTS

Hereafter, embodiments according to the present invention will bedescribed in detail with reference to the drawings.

FIG. 1 is a view showing a setting value management system 10 thatincludes an image forming apparatus according to the embodiment.

As shown in FIG. 1, the setting value management system 10 consists of amanagement server 204, terminals 206 and 209, and a managed objectapparatus group 205 that contains a plurality of image formingapparatuses (five sets in FIG. 1). Each of the image forming apparatusesof the managed object apparatus group 205, the management server 204,and the terminal 206 are connected to a network 203. Moreover, theterminal 206 and the terminal 209 are connected to the Internet 207.Furthermore, image forming apparatuses 201 and 202 are selected fromamong the various image forming apparatuses for description. An imageforming apparatus is an example of a data processing apparatus.

The image forming apparatuses 201 and 202 read originals and form imagesthereof on recording sheets etc.

Moreover, the image forming apparatuses 201 and 202 can receive imagedata read by another image forming apparatus and PDL data generated by aclient computer (not shown) via the network 203 and can output them.

Furthermore, the image data read by the image forming apparatus 201 or202 can be transmitted to various apparatuses, such as a file server anda mail server that are not shown through the network 203.

The management server 204 is connected with the image formingapparatuses of the managed object apparatus group 205 through thenetwork 203, and communicates to export and import setting values.Well-known protocols, such as HTTP (Hyper Text Transfer Protocol), SOAP(Simple Object Access Protocol), and FTP (File Transfer Protocol), areused for this communication.

The terminal 206 in remote user environment has the same function as themanagement server 204, and is connected with the terminal 209 in remotemaintenance service environment through the Internet 207 as mentionedabove.

Thereby, the terminal 209 operates the terminal 206 in the remote userenvironment so as to make the image forming apparatus of the managedobject apparatus group 205 export the setting values to store them, andso as to import the setting values that are stored in the terminal 206.

Moreover, the image forming apparatuses 201 and 202 export the settingdata to a USB storage device 208 according to a user's operation withoutusing the managing server 204, and import the setting data that isstored in the USB storage device 208.

FIG. 2 is a block diagram schematically showing a configuration of theimage forming apparatus 201 shown in FIG. 1. The image forming apparatus201 will be described as the representative of the managed objectapparatus group 205. The configuration described in FIG. 2 is common tothe image forming apparatuses of the managed object apparatus group 205.

As shown in FIG. 2, the image forming apparatus 201 consists of a maincontroller 100, a subcontroller 101, an operation panel 103, an LCDpanel 104, a scanner 105, and a printer 106.

The main controller 100 consists of a CPU 108, a RAM 109, an operationunit interface 112, a network interface 113, an external serialinterface 114, a flash ROM 110, an HDD 111, and a bus bridge 116. Theseare connected via a system bus 115.

The CPU 108 controls the entire main controller 100. The RAM 109 is usedas a main memory and a work area of the CPU 108, and stores image data.The operation unit interface 112 is an interface between the maincontroller 100 and an operation unit that consists of the LCD panel 104and the operation panel 103. The LCD panel 104 is united with a touchpanel. The LCD panel 104 displays information to a user. The touch panelallows a user to operate. Moreover, the operation panel 103 consists ofhard buttons, such as a ten key pad and a start key.

The network interface 113 is an NIC, for example, and is an interfacebetween the main controller 100 and a LAN 102. Thereby, the imageforming apparatus 201 exchanges data bidirectionally with anothernetworking device or a file server through the LAN 102.

In the embodiment, the external serial interface 114 is a USB interfaceto which an external device, such as a memory-media reader or an IC cardreader, is connected to exchange data bidirectionally.

In the embodiment, a device setting file is exchanged through thenetwork interface 113 or the external serial interface 114 at the timeof import and export.

The flash ROM 110 and the HDD 111 stores image data, the setting valuesof the image forming apparatus 201, and programs that are executed bythe CPU 108. In the embodiment, the data of setting values that isimported and exported is stored in the HDD 111.

The bus bridge 116 connects the buses of the main controller 100 and thesubcontroller 101.

The subcontroller 101 consists of a CPU 117, a RAM 118, a memorizedimage processing unit 123, a device interface 120, a scanner imageprocessing unit 121, a printer image processing unit 122, and a modem125. These are connected via a system bus 127.

The CPU 117 controls the entire subcontroller 101. The RAM 118 is usedas a main memory and a work area of the CPU 117, and stores image data.

The memorized image processing unit 123 applies an image process toimage data stored in the RAM 118, and stores again the processed imagedata into the RAM 118. The image process includes rotation, scaling,color space conversion, gray scale conversion, composition, encoding,decoding, etc.

The CPU 117 stores the image data stored in the RAM 118 to the flash ROM110 or the HDD 111 of the main controller 100 through the bus bridge 116after the image process applied by the memorized image processing unit123.

The device interface 120 is an interface between the devices, which arethe scanner 105 and the printer 106, and the subcontroller 101. Thescanner 105 and the printer 106 exchange signals, such as a controlsignal, with the CPU 117 via the device interface 120.

The scanner 105 reads an image of an original and acquires image data ofthe image. The image data read is stored into the RAM 118 through thescanner image processing unit 121. An automatic document feeder may beattached to this scanner 105 in order to read originals automatically.

The printer 106 forms an image on a recording medium like paper with anelectrophotographic system or an ink jet system, for example. The CPU117 stores the image data stored in the flash ROM 110 or the HDD 111 ofthe main controller 100 to the RAM 118 via the bus bridge 116, andoutputs it to the printer 106 via the printer image processing unit 122.

The scanner image processing unit 121 and the printer image processingunit 122 perform image processing, such as color space conversion,movement, color adjustment, concentration control, and delay control.The modem 125 connects to a public line 107, and modulates and restoressignals during facsimile transmission and reception.

FIG. 3 is a block diagram schematically showing a functionalconfiguration of the image forming apparatus 201 in the managed objectapparatus group 205 shown in FIG. 1.

The image forming apparatus 201 will be described as the representativeof the managed object apparatus group 205. The configuration describedin FIG. 3 is common to the image forming apparatuses of the managedobject apparatus group 205. Moreover, the image forming apparatus 201supports Unicode.

FIG. 3 shows the function for importing and exporting the setting data.Moreover, an import service requester 301 and a USB storage device 208are configurations outside the image forming apparatus.

Furthermore, an intranet 302 is a part of the network 203. It should benoted that a symbol “DB” used in the following description represents adatabase. Moreover, a device-setting file that includes address bookdata, departmental management data, and device-setting data is used asdata imported or exported.

A process relevant to the import will be described. First, a networkimport process that imports data via the network will be described.

The import service requester 301 sends a device setting file, and theimport service provider 300 receives a device setting file. The importservice requester 301 and the import service provider 300 communicateusing an SOAP message via the intranet 302.

After an HTTP server 303 and an SOAP server 304 interpret a requestmessage, a device-setting-import CGI 306 of a network import unit 305corresponding to a process applicable to the message is started. Anetwork import module 307 executes the process in response to a request.

The SOAP server 304 starts the device-setting-import CGI 306 inaccordance with a service request. The device-setting-import CGI 306started makes the network import module 307 primarily store the receiveddevice setting file into a temporary area 320.

The device setting file stored primarily is configured in a compressedformat that converged a plurality of XML files. After finishing theprimary storing, the network import module 307 requires a secondarystoring from a device setting management module 309.

The device setting management module 309 reads the device setting filecompressed from the temporary area 320, and performs a decompressionprocess. When the decompression process is successful, adevice-setting-file DB 310 is initialized. The above-mentioned temporaryarea 320 and the device-setting-file DB 310 are stored in the HDD 111.

When the initialization succeeded, an item of the acquired setting itemname is registered to the applicable device-setting-file DB 310, whileparsing the device setting file acquired by the decompression.

The device setting management module 309 requires tertiary storing froman import module 321 of a setting-value import unit 313 for control. Thesetting data described in the device setting file becomes effective inan actual device control by this tertiary storing.

The import module 321 that received the request acquires the settingdata corresponding to the setting item name of a processing object fromthe device-setting-file DB 310, and registers it into asetting-management DB 322 for control.

This setting-management DB 322 is stored in the HDD 111, is a DB intowhich a plurality of sets of setting data containing character stringdata about the control of the image forming apparatus 201 areregistered, and consists of three DBs. As mentioned above, the devicesetting file includes three kinds of data that are the device settingdata, the departmental management data, and the address book data. Amongthese, the device setting data is registered into a device-setting DB315. The departmental management data is registered into adepartmental-management-setting DB 317. The address book data isregistered into an address book DB 319.

Accordingly, a device-setting import module 314 reads onlydevice-setting data one-by-one from among a plurality of kinds ofsetting data contained in the device-setting file, and registers it intothe device-setting DB 315.

A departmental-management-setting import module 316 reads onlydepartmental management data from among the plurality of kinds ofsetting data contained in the device-setting file, and registers it intothe departmental-management-setting DB 317.

An address book import module 318 reads only address book data fromamong the plurality of kinds of setting data contained in the devicesetting file, and registers it into the address book DB 319.

Next, the import process from the USB storage device 208 will bedescribed. A USB import module 312 performs an import process from theUSB storage device 208 instead of the network import unit 305.

The USB import module 312 detects that the device configuration file isstored in the USB storage device 208. The USB import module 312 requiresthe secondary storing from the device setting management module 309after storing the device setting file into the temporary area 320. Theimport operation thereafter this is similar to the network importprocess.

A process relevant to the export will be described. First, a networkexport process that exports data via the network will be described.

When receiving an export request via the intranet 302, the importservice provider 300 requires the device-setting management module 309to generate an export file.

When receiving the request to generate the export file, thedevice-setting management module 309 makes the device-setting-file DB310 store the information set exported to the import module 321.

When the import module 321 stores the setting data to be exported intothe device-setting-file DB 310, the device setting management module 309generates a device-setting file in the temporary area 320.

This device-setting file describes the setting data that was stored intothe device-setting-file DB 310 in XML.

When compressing the device setting file, the device-setting managementmodule 309 notifies an export request source of a completion ofgenerating the device-setting file through the import service provider300 and the intranet 302.

Then, when the import service provider 300 receives the request of thedevice-setting file through the intranet 302, the device-settingmanagement module 309 sends the created device setting file to theexport request source.

Next, an export process to the USB storage device 208 will be described.When a user requests export to the USB storage, the USB import module312 require export from the device-setting management module 309.

Thereafter, the process similar to the network export is performed, andthe USB import module 312 requires the device-setting file from thedevice-setting management module 309 when the completion of generating adevice setting file is notified.

The USB import module 312 stores the device-setting file received fromthe device-setting management module 309 into the USB storage device208. Thus, the device setting file is exported to the USB storage device208.

Although import and export are controlled by the same module, they maybe controlled by different modules.

FIG. 4 is a view showing an example of the setting data read from thedevice-setting file DB 310 by the device-setting management module 309shown in FIG. 3.

As shown in FIG. 4, items of the setting data to be read includes“SettingDataName”, “KeyName”, “Type”, “Size”, “Value”, and“ConversionFlag”.

The “SettingDataName” expresses name of setting data. The “KeyName”expresses the setting data name in detail where necessary. The “Type”expresses a data type of the “Value”. For example, “string” means astring type and “int” means an integer type. The “Size” expresses a datasize of the “Value”. Among these, especially the “Value” of the “string”type is character string data.

Moreover, the “ConversionFlag” expresses a conversion flag that is usedto determine whether a character string shown in the “Value” shouldsupport another character code. That is, it is used to determine whetherthe character string should be converted. The value “1” of theconversion flag indicates that the character string should be convertedinto another character code. The value “0” of the conversion flagindicates that the character string is not converted into anothercharacter code.

Thus, the “KeyName” is assigned to every setting data. In FIG. 4, two“KeyNames” (“device_name” and “device_name_utf8”) are assigned to thesetting data of the device name that indicates the name of the imageforming apparatus.

Moreover, the “device_name” is a string type and the maximum data sizeis 16 bytes.

Furthermore, the “device_name_utf8” is the setting data that indicatethe same name as the “device_name” in a different character code. Inthis image forming apparatus, the setting of the character string dataof the “device_name_utf8” is effective, and the “device_name” is merelyprepared as management information.

Actually, although the “Value” of the “device_name_utf8” is thecharacter string of “X′695243E4b880E58FB7E6A99F′”, the “Value” of the“device_name” is blank.

FIG. 5 is a view showing an example of a device setting file generatedby the device setting management module 309 shown in FIG. 3.

As shown in FIG. 5, the device setting file is described in XML asmentioned above. Hereinafter, each tag will be described.

First, the tag <lang> indicates the language setting of the imageforming apparatus. A code “jp” means Japanese setting. Moreover, the tag<device_settings> indicates a device-setting file.

Furthermore, the tag <device_name_utf8 size=“32” type=“string”>corresponds to the device name of the “device_name_utf8” in FIG. 4.Moreover, the size is 32 bytes and the type is a character string aswell as that shown in FIG. 4. The same size and type as that shown inFIG. 4 are indicated in each of the following tags.

The tag <device_name_size=“16” type=“string”>corresponds to the devicename of the “device_name” in FIG. 4.

The tag <device_location_utf8 size=“32” type=“string”> corresponds tothe device location of the “device_location_utf8” in FIG. 4.

The tag <device_location_size=“16” type=“string”> corresponds to thedevice location of the “device_location” in FIG. 4.

The tag <summer_time_settings_size=“44” type=“binary”> corresponds tothe summer time setting in FIG. 4.

The tag <auto_clear_time_size=“4” type=” int”> corresponds to the autoclear time in FIG. 4.

The tag <fax_receive_mode_size=“2” type=” u16”>corresponds to the FAXreception mode in FIG. 4.

For example, the setting data of which the “KeyName” is the“device_name_utf8” is the string type data in 32 bytes, is the characterstring data indicated by the “Value” specified by the “KeyName” as thetag, and has the attributes indicated by the “Size” and “Type”.

The above-mentioned device-setting file is an exported file indicatingthat the file was exported after adding code information that indicatesthe character code of the character string data concerned to thecharacter string data to be exported. The code information is the“device_name” or “device_name_utf8” that exists in the tag in which thecharacter string is included, when the “Type” is “string”. The codeinformation is the second character code in the case of the“device_name”, and it is the first character code in the case of the“device_name_utf8”.

FIG. 6 is a view showing a language setting of the image formingapparatus 201 shown in FIG. 2.

As shown in FIG. 6, two kinds of character codes are prepared like thefirst and second character codes for one language. For example, thefirst character code UTF-8 and the second character code Shift-JIS areprepared for Japanese. Moreover, the first character code is Unicode inany language setting.

Thus, the language settings as shown in FIG. 6 are established in orderto support different character codes. However, more than two kinds ofcharacter codes may be prepared for one language.

FIG. 7 is a flowchart showing a device-setting-file generation processexecuted by the CPU 108 shown in FIG. 2.

The device-setting-file generation process shown in FIG. 7 is executedat the time of export. The data of the address book DB 319, thedepartmental-management-setting DB 317, and the device-setting DB 315 iscopied to the device-setting-file DB 310 in advance.

Moreover, the tags <?xml version=“1.0” encoding=“utf-8” ?>, <lang>, and<device_settings> shown in FIG. 5 shall be written into thedevice-setting file at the time of starting the process.

As shown in FIG. 7, the device-setting management module 309 reads oneitem of the setting data exported from the device-setting-file DB 310(step S401). Thus, since the setting data is read one-by-one, theprocess loops for the number of the items of the setting data (thenumber of setting values). Moreover, when all the items of the settingdata have been read, no data was read in the step S401.

Next, the CPU 108 determines whether any setting data was read (stepS402). When no data was read (NO in the step S402), this process isfinished. After finishing the process, the device-setting file describedin XML will be compressed.

On the other hand, when any setting data was read (YES in the stepS402), the CPU 108 determines whether the “Value” is empty (step S403).Empty of the “Value” means that the “Value” is blank like the “Value” ofthe “device_name” in FIG. 4, for example.

When the “Value” is empty (YES in the step S403), the process returns tothe step S401.

On the other hand, when the “Value” is not empty (NO in the step S403),the CPU 108 adds the setting data read to the device-setting file (stepS404).

Next, the CPU 108 determines whether the conversion flag is equal to “1”(step S405). When the conversion flag is not equals to “1” (NO in thestep S405), the process returns to the step S401.

On the other hand, when the conversion flag is equal to “1” (YES in thestep S405), the character code of the character string data is converted(step S406). Then, the character string data of which the character codewas converted is added to the device-setting file (step S407), and theprocess returns to the step S401.

The conversion of the character code in the step S406 will be described.For example, in the case shown in FIG. 4, the CPU 108 will add thesetting data indicated by the “device_name” that is the “KeyName”acquired by deleting the suffix “_utf8” from the “device_name_utf8”.

Since the “Value” of the “device_name” is empty in this case, thecharacter string data that is acquired by converting the “Value” of the“device_name_utf8” into the second character code is used as the “Value”of the “device_name”.

Thus, the process in the step S406 corresponds to the conversion unit.That is, when the character string data in the second character code,which is different from the first character code of the character stringdata registered in the device-setting-file DB 310, is exported, thecharacter string data is converted into the second character code in thestep S406. As a result, the garbling of characters caused by thedifference among the character codes is reduced.

More specifically, when the code information indicates the firstcharacter code (_utf8) and the conversion flag indicates conversion (YESin the step S405), the character string data is converted into thesecond character code in the step S406. Moreover, the process in thestep S407 corresponds to the export unit. That is, the CPU 108 exportsthe character string data converted into the second character code inaddition to the setting data registered in the device-setting-file DB310 in the step S407.

The CPU 108 determines the kind of the second character code accordingto the language setting shown in FIG. 6. In the case shown in FIG. 6,the first character code UTF-8 and the second character code Shift-JISare prepared for Japanese.

In this case, the character string data “X′695243E4b880E58FB7E6A99F′” inUTF-8 is converted into Shift-JIS to be the character string data“X′69524388EA8D868B40′”. The conversion result is shown as an element ofthe tag <device_name . . . > in FIG. 5.

Such a process is repeated until all the items of the setting data havebeen read, and the device-setting file is generated in the XML formatusing the tags of the “KeyName” corresponding to each setting data.

In the device-setting-file generation process shown in FIG. 7, the CPU108 determines whether the setting data is converted into the secondcharacter code in the step S404 for every item of the setting data.However, the CPU 108 determines whether the setting data is convertedinto the second character code before exporting, based on a user'sinstruction. That is, it is able to set so as to determine whether thedevice-setting data is converted or not regardless of the value of theconversion flag.

If the selection result instructs not to convert into the secondcharacter code, the process returns to the step S401 without convertingthe character string data in the step S404 regardless of the value (“0”or “1”) of the conversion flag.

Moreover, although the setting data is managed in association with aninherent character string like the “KeyName” in this embodiment, what isnecessary is just a unique identifier, and it is not limited tomanagement by a character string like the “KeyName”.

Furthermore, although the first character code is UTF-8 and the secondcharacter code is Shift-JIS in FIG. 6, the combination of charactercodes is not necessarily limited to this.

Moreover, the device-setting file may consist of a plurality of filesfor kinds of the setting data. Moreover, although the device-settingfile is generated in the XML format, it may be generated in anotherformat.

Next, an import process will be described. In the embodiment, thedevice-setting management module 309 initializes the device-setting-fileDB 310 before performing the import process. Moreover, if thedevice-setting file to be imported is compressed, the file isdecompressed.

FIG. 8 is a view showing contents of the device-setting-file DB 310initialized by the device setting management module 309.

As shown in FIG. 8, the “Value” for every setting data is blank, whichshows there is no imported data. If the import process is performed,setting data described in a device-setting file is registered into thisinitialized device-setting-file DB 310.

FIG. 9 is a flowchart showing procedures of a registration processexecuted by the CPU 108 shown in FIG. 2 to register a device settingfile to the device-setting-file DB 310. It should be noted that adescription of FIG. 9 uses the device-setting file shown in FIG. 10 asan example. As shown in FIG. 10, the code information(“device_name_utf8”, “device_name”, etc.) that shows the character codeof the character string data concerned is added to the character stringdata to be imported.

As shown in FIG. 9, the CPU 108 parses the device-setting file andanalyzes, and reads the setting data to be imported below the tag<device_settings> one-by-one (step S801). Thus, since the setting datais read one-by-one, the process loops for the number of the items of thesetting data (the number of setting values). Moreover, when all theitems of the setting data have been read, no data was read in the stepS801.

Next, the CPU 108 determines whether any setting data was read (stepS802). When no setting data was read (NO in the step S802), this processis finished.

On the other hand, when any setting data was read (YES in the stepS802), the CPU 108 determines whether the setting data is import objectdata (step S803). Specifically, when the “KeyName” of the setting dataread in the step S801 has been already registered in thedevice-setting-file DB, the setting data is considered as import objectdata. For example, since the “summer_time_settings” in thedevice-setting file shown in FIG. 10 has not been registered in thedevice-setting-file DB shown in FIG. 8, it is not considered as importobject data. Moreover, since the “KeyName” of “device_name_utf8” hasbeen already registered in the device-setting-file DB, it becomes importobject data.

When the setting data is not import object data (NO in the step S803),the process returns to the step S801.

On the other hand, when the setting data is import object data (YES inthe step S803), the CPU 108 determines whether the item of the settingdata is an item in the second character code (step S804). For example,the item of which the “KeyName” in FIG. 8 does not include “utf8” and ofwhich the conversion flag is “1” is determined as an item in the secondcharacter code.

When the item of the setting data is not an item in the second charactercode (NO in the step S804), the CPU 108 registers the setting data intothe device-setting-file DB 310 (step S807), and returns the process tothe step S801.

On the other hand, when the item of the setting data is an item in thesecond character code (YES in the step S804), the CPU 108 determineswhether the data of the item concerned has been already registered inthe corresponding item in the first character code (step S805).

Specifically, the CPU 108 determines whether the “Value” of the“KeyName” to which “_utf8” is added behind the “KeyName” is empty. Forexample, the CPU 108 determines whether the data has been alreadyregistered in the first character code into the item“device_location_utf8” corresponding to the item “device_location”. Whenthe “Value” is not empty, the CPU 108 determines that the data has beenalready registered in the first character code.

When the data has been already registered in the first character code(YES in the step S805), the process returns to the step S801.

On the other hand, when the data has not been registered in the firstcharacter code (NO in the step S805), the CPU 108 converts the settingdata into the first character code (step S806). For example, the settingdata “X′33328EC08CB18EBA′” of the item <device_location> is convertedinto the first character code. The process in the step S806 correspondsto the conversion unit. That is, when the character code of thecharacter string data of the setting data that should be imported intothe device-setting-file DB 310 is the second character code, which isdifferent from the first character code that is the character code ofthe character string data registered into the device-setting-file DB310, the CPU 108 converts the character string data into the firstcharacter code in the step S805. As a result, the garbling of characterscaused by the difference among the character codes is reduced.

More specifically, when the code information about the character stringdata to be imported is the second character code (YES in the step S804)and when the character string data converted into the first charactercode has not been imported (NO in the step S805), the CPU 108 convertsthe character string data into the first character code.

Next, the CPU 108 registers the setting data converted into the firstcharacter code into the device-setting-file DB 310 (step S807), andreturns the process to the step S801. For example, the CPU 108 registersthe setting data “X′3332E5AE9FE9A893E5AEA4” of the item<device_location> that was acquired by converting the setting data“X′33328EC08CB18EBA′” into the first character code. The process in thestep S407 corresponds to the import unit. That is, the CPU 108 performsthe import by registering the converted character string data in placeof the character string data in the second character code into thedevice-setting-file DB 310.

It should be noted that the second character code (Shift-JIS) isconverted into the first character code (UTF-8) based on Japanese (jp)setting defined by the tag <lang> in FIG. 10 with reference to thelanguage setting shown in FIG. 6.

Moreover, although the CPU 108 determines that the data is the secondcharacter code data because the “KeyName” includes the “utf8” and theconversion flag is “1” in the step S804, any other information may beused as long as the attribute of the item can be determined based on theinformation concerned.

FIG. 11 is a view showing contents of the device-setting-file DB 310after the registration process shown in FIG. 10.

As shown in FIG. 11, the “Value” of the item “device_name” and the“Value” of the item “device_location” are empty, because the result inthe step S804 is YES (the conversion flag is “1”) and the data is notregistered in the second character code in the step S807. Since the datafor the items “device_name_utf8” and “device_location_utf8” areconverted into the first character code in the step S806 and areregistered in the first character code in the step S807, the “Values”therefor are not empty.

When the registration to the device-setting-file DB 310 finishesaccording to the registration process in FIG. 10, the import module 321reflects the contents of the device-setting-file DB 310 to thesetting-management DB 322.

FIG. 12A is a view showing a screen before import displayed on the LCDpanel 104 shown in FIG. 2. FIG. 12B is a view showing a screen after theimport displayed on the LCD panel 104 shown in FIG. 2.

Moreover, columns for “DEVICE NAME” and “LOCATION” in each screencorrespond to the “device_name_utf8” and the “device_location_utf8”,respectively.

Although the columns for “DEVICE NAME” and “LOCATION” are blank in FIG.12A, the imported character strings are displayed in the columns in FIG.12B.

FIG. 13A is a view showing contents of the device-setting-file DB 310before registering the contents of the device setting file shown in FIG.10 into an image forming apparatus that employs a different charactercode. FIG. 13B is a view showing contents of the device-setting-file DB310 after registering the contents of the device setting file shown inFIG. 10 into the image forming apparatus that employs the differentcharacter code.

As shown in FIG. 13A, the setting data names do not include items“device_name_utf8” and “device_location_utf8”, and all the conversionflags are “0”.

In this case, the determination result in the step S804 is NO for everyitem, only the setting data of items of which “KeyNames” are common inFIG. 10 and FIG. 13A are registered into the device-setting-file DB 310without converting the character code.

As a result, as shown in FIG. 13B, the character strings are registeredas the “Values” for the items “device_name” and “device_location” in thesecond character code as-is.

Although the import and export of the partial setting data in the imageforming apparatus were described in the above-mentioned embodiment, theembodiment is applicable to all the setting data in an image formingapparatus.

Other Embodiments

Aspects of the present invention can also be realized by a computer of asystem or apparatus (or devices such as a CPU or MPU) that reads out andexecutes a program recorded on a memory device to perform the functionsof the above-described embodiment(s), and by a method, the steps ofwhich are performed by a computer of a system or apparatus by, forexample, reading out and executing a program recorded on a memory deviceto perform the functions of the above-described embodiment(s). For thispurpose, the program is provided to the computer for example via anetwork or from a recording medium of various types serving as thememory device (e.g., computer-readable medium).

While the present invention has been described with reference toexemplary embodiments, it is to be understood that the invention is notlimited to the disclosed exemplary embodiments. The scope of thefollowing claims is to be accorded the broadest interpretation so as toencompass all such modifications and equivalent structures andfunctions.

This application claims the benefit of Japanese Patent Application No.2012-120583, filed on May 28, 2012, which is hereby incorporated byreference herein in its entirety.

What is claimed is:
 1. A data processing apparatus comprising: a storageunit configured to store setting data for the data processing apparatus;a receiving unit configured to receive an instruction for exporting thesetting data stored in said storage unit; a converting unit configuredto convert Unicode data included in the setting data into character codedata of language, which is set to the data processing apparatus; and anexport unit configured to export the character code data converted bysaid converting unit and the Unicode data.
 2. The data processingapparatus according to claim 1, wherein said export unit exports thesetting data and code information that shows the character code of thesetting data concerned.
 3. The data processing apparatus according toclaim 2, wherein code information about the setting data and aconversion flag that shows whether the character code data should beconverted by said converting unit are registered in said storage unitfor every setting data registered, and wherein said conversion unitconverts the Unicode data when the code information shows Unicode andthe conversion flag shows to convert.
 4. The data processing apparatusaccording to claim 3, wherein said converting unit determines whetherthe setting data is converted into the character code data, based on auser's instruction.
 5. A data processing apparatus comprising: a storestorage unit configured to store setting data for the data processingapparatus; a receiving unit configured to receive an instruction forimporting setting data of the data processing apparatus; a convertingunit configured to convert character code data included in the settingdata that is not Unicode data into Unicode data; and an import unitconfigured to import the Unicode data converted by said converting unitwhen the setting data imported according to an instruction received bysaid receiving unit is not Unicode data, and to import data withoutconversion by said converting unit when the setting data importedaccording to the instruction is Unicode data.
 6. The data processingapparatus according to claim 5, wherein code information that shows thecharacter code of the setting data is added to the setting dataimported, and wherein said converting unit converts the character codedata included in the setting data that is not Unicode data into theUnicode data when the code information about the setting data to beimported shows the character code of the language set in the dataprocessing apparatus, and when the setting data converted into Unicodehas not imported.
 7. A control method for a data processing apparatuscomprising: storing setting data for the data processing apparatus;receiving an instruction for exporting the stored setting data;converting Unicode data included in the setting data into character codedata of language, which is set to the data processing apparatus; andexporting the character code data converted in said converting and theUnicode data.
 8. A control method for a data processing apparatuscomprising: storing setting data for the data processing apparatus;receiving an instruction for importing setting data for the dataprocessing apparatus; converting character code data included in thesetting data that is not Unicode data into Unicode data; and importingthe Unicode data converted by said converting when the setting dataimported according to an instruction received in said receiving is notUnicode data, and importing data without converting when the settingdata imported according to the instruction is Unicode data.
 9. Anon-transitory computer-readable storage medium storing acomputer-readable program and the program computer executable codes toperform a control method for a data processing apparatus, the controlmethod comprising: storing setting data for the data processingapparatus; receiving an instruction for exporting the stored settingdata; converting Unicode data included in the setting data intocharacter code data of language, which is set to the data processingapparatus; and exporting the character code data converted in saidconverting and the Unicode data.
 10. A non-transitory computer-readablestorage medium storing a computer-readable program and the programcomputer executable codes to perform a control method for a dataprocessing apparatus, the control method comprising: storing settingdata for the data processing apparatus; receiving an instruction forimporting setting data for the data processing apparatus; convertingcharacter code data included in the setting data that is not Unicodedata into Unicode data; and importing the Unicode data converted by saidconverting when the setting data imported according to an instructionreceived by said receiving unit is not Unicode data, and importing datawithout converting when the setting data imported according to theinstruction is Unicode data.